Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

client/client_test.go (1)

1251-1251: 🚀 Performance & Scalability | 🔵 Trivial | ⚡ Quick win

Remove fixed sleep from test setup.

time.Sleep(1 * time.Second) makes the test slower and can still be flaky as a readiness mechanism; prefer relying on startTestServerWithPort readiness (or polling the endpoint with timeout if needed).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@client/client_test.go` at line 1251, The test setup in client_test.go uses a
fixed time.Sleep as a readiness wait, which slows the suite and can still be
flaky. Remove the sleep from the test flow around startTestServerWithPort and
rely on the server’s readiness signal instead; if readiness is still uncertain,
replace it with a bounded polling check against the endpoint using a timeout.
Keep the change localized to the test helper or setup path that currently waits
before proceeding.

client/core.go (1)

116-127: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Eligibility logic is correct; consider deduplicating the repeated method check.

The QUERY addition is sound: per RFC 10008 QUERY is safe/idempotent, and transport.go only downshifts POST→GET on 301/302/303, so QUERY (like GET/HEAD) follows redirects preserving method and body. The identical three-method condition is now duplicated across the retry and non-retry branches; extracting a small helper would keep them from drifting.

♻️ Extract redirect-eligibility helper

func shouldFollowRedirects(method string, maxRedirects int) bool {
	return maxRedirects > 0 &&
		(method == fiber.MethodGet || method == fiber.MethodHead || method == fiber.MethodQuery)
}

-				if c.req.maxRedirects > 0 && (string(reqv.Header.Method()) == fiber.MethodGet || string(reqv.Header.Method()) == fiber.MethodHead || string(reqv.Header.Method()) == fiber.MethodQuery) {
+				if shouldFollowRedirects(string(reqv.Header.Method()), c.req.maxRedirects) {
 					return c.client.DoRedirects(reqv, respv, c.req.maxRedirects)
 				}
 				return c.client.Do(reqv, respv)
 			})
 		} else {
-			if c.req.maxRedirects > 0 && (string(reqv.Header.Method()) == fiber.MethodGet || string(reqv.Header.Method()) == fiber.MethodHead || string(reqv.Header.Method()) == fiber.MethodQuery) {
+			if shouldFollowRedirects(string(reqv.Header.Method()), c.req.maxRedirects) {
 				err = c.client.DoRedirects(reqv, respv, c.req.maxRedirects)
 			} else {
 				err = c.client.Do(reqv, respv)
 			}
 		}

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@client/core.go` around lines 116 - 127, The redirect eligibility check in
core.go is duplicated in both the retry and non-retry branches, so extract it
into a small helper to prevent the method list from drifting. Add a helper such
as shouldFollowRedirects and use it from the logic around c.client.DoRedirects
and c.client.Do so the GET/HEAD/QUERY condition is defined once and reused
consistently.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes